Video client management of video service feature flags

ABSTRACT

At a video content network client, obtain, from a remote targeted feature flag configuration server of the video content network, feature flag overrides associated with the client. Send, from the video content network client, to a remote back-end server of the video content network; the feature flag overrides. At the video content network client, obtain, from the remote back-end server, data to be rendered in accordance with an updated feature flag profile including both default feature flag values and feature flag values overridden in accordance with the feature flag overrides. Render the data on the video content network client.

FIELD OF THE INVENTION

The present invention relates generally to the electrical, electronic,and computer arts, and more particularly relates to video contentnetworks and the like.

BACKGROUND OF THE INVENTION

With the advent of digital communications technology, TV program streamsare typically transmitted in digital formats. For example, DigitalSatellite System (DSS), Digital Broadcast Services (DBS), and AdvancedTelevision Standards Committee (ATSC) program streams are digitallyformatted pursuant to the well-known Moving Pictures Experts Group 2(MPEG-2) standard. The MPEG-2 standard specifies, among other things,the methodologies for video and audio data compression allowing formultiple programs, with different video and audio feeds, to bemultiplexed in a transport stream traversing a single transmissionchannel. A digital TV receiver may be used to decode an MPEG-2 encodedtransport stream, and extract the desired program therefrom.

The compressed video and audio data are typically carried by continuouselementary streams, respectively, which are broken into access units orpackets, resulting in packetized elementary streams (PESs). Thesepackets are identified by headers that contain time stamps forsynchronizing, and are used to form MPEG-2 transport streams. Fordigital broadcasting, multiple programs and their associated PESs aremultiplexed into a single transport stream. A transport stream has PESpackets further subdivided into short fixed-size data packets, in whichmultiple programs encoded with different clocks can be carried. Atransport stream not only includes a multiplex of audio and video PESs,but also other data such as MPEG-2 program specific information(sometimes referred to as metadata) describing the transport stream. TheMPEG-2 metadata may include a program associated table (PAT) that listsevery program in the transport stream. Each entry in the PAT points toan individual program map table (PMT) that lists the elementary streamsmaking up each program. Some programs are open, but some programs may besubject to conditional access (encryption), and this information (i.e.,whether open or subject to conditional access) is also carried in theMPEG-2 transport stream, typically as metadata.

The aforementioned fixed-size data packets in a transport stream eachcarry a packet identifier (PID) code. Packets in the same elementarystreams all have the same PID, so that a decoder can select theelementary stream(s) it needs and reject the remainder.Packet-continuity counters may be implemented to ensure that everypacket that is needed to decode a stream is received.

Video on demand (VOD) systems allow users to select and watch videocontent over a network. Some VOD systems “stream” content for real-timeviewing. Others “download” the content to a set-top box before viewingstarts. Use of digital video recorders (DVRs), also known as personalvideo recorders (PVRs), is ubiquitous. A “network PVR (NPVR)” (alsoreferred to as an NDVR (Network Digital Video Recorder)) service allowsthe user to perform the analogous DVR functions through use of anetwork, rather than via a local DVR at the user premises.

Video clients often call into back-end systems to obtain the data theyneed to display guide and on-demand menu pages (which show,respectively, programming that is available via broadcast or on-demand).The back-end systems typically have to manage feature flags so as not toreturn new features to clients that are not expecting those features.Usually, there is a careful back-end/front-end release coordination,allowing for a release that all users obtain at the same time.

SUMMARY OF THE INVENTION

Techniques are provided for video client management of video servicefeature flags. In one aspect, an exemplary method includes, at a videocontent network client, obtaining, from a remote targeted feature flagconfiguration server of the video content network, feature flagoverrides associated with the client; sending, from the video contentnetwork client, to a remote back-end server of the video contentnetwork; the feature flag overrides; at the video content networkclient, obtaining, from the remote back-end server, data to be renderedin accordance with an updated feature flag profile including bothdefault feature flag values and feature flag values overridden inaccordance with the feature flag overrides; and rendering the data onthe video content network client.

In another aspect, an exemplary video content network system isconnected to at least one client and includes a remote targeted featureflag configuration server that provides, to the client, feature flagoverrides associated with the client; and a remote back-end server thatobtains, from the client, the feature flag overrides, and provides, tothe client, data to be rendered in accordance with an updated featureflag profile including both default feature flag values and feature flagvalues overridden in accordance with the feature flag overrides.

In another aspect, an exemplary method includes providing, from a remotetargeted feature flag configuration server of a video content networksystem, to a client, feature flag overrides associated with said client;obtaining, at a remote back-end server, from said client, said featureflag overrides; and providing, from said remote back-end server, to saidclient, data to be rendered in accordance with an updated feature flagprofile comprising both default feature flag values and feature flagvalues overridden in accordance with said feature flag overrides.

As used herein, “facilitating” an action includes performing the action,making the action easier, helping to carry the action out, or causingthe action to be performed. Thus, by way of example and not limitation,instructions executing on one processor might facilitate an actioncarried out by instructions executing on a remote processor, by sendingappropriate data or commands to cause or aid the action to be performed.For the avoidance of doubt, where an actor facilitates an action byother than performing the action, the action is nevertheless performedby some entity or combination of entities.

One or more embodiments of the invention or elements thereof can beimplemented in the form of an article of manufacture including a machinereadable medium that contains one or more programs which when executedimplement one or more method steps set forth herein; that is to say, acomputer program product including a tangible computer readablerecordable storage medium (or multiple such media) with computer usableprogram code for performing the method steps indicated. Furthermore, oneor more embodiments of the invention or elements thereof can beimplemented in the form of an apparatus (e.g., a client, targetedfeature flag configuration server, back-end server, or any two or moreof them networked as a system) including a memory and at least oneprocessor that is coupled to the memory and operative to perform, orfacilitate performance of, exemplary method steps. Yet further, inanother aspect, one or more embodiments of the invention or elementsthereof can be implemented in the form of means for carrying out one ormore of the method steps described herein; the means can include (i)specialized hardware module(s), (ii) software and/or firmware module(s)stored in a tangible computer-readable recordable storage medium (ormultiple such media) and implemented on a hardware processor, or (iii) acombination of (i) and (ii); any of (i)-(iii) implement the specifictechniques set forth herein. The means do not include a transmissionmedium per se or a disembodied signal per se.

Techniques of the present invention can provide substantial beneficialtechnical effects. For example, one or more embodiments provide one ormore of the following:

-   -   Ability for client engineers to test or integrate against        backend feature changes without affecting all users of that        backend system;    -   Techniques wherein coordination of testing backend changes on        the client becomes a small, low-risk issue as only the tester's        account can be affected;    -   Techniques wherein development of partially completed features        can be deployed to shared environments as only accounts with the        feature enabled will see the partially completed changes;    -   improving the performance of a content network or the like by        reducing security risk and/or downtime during new feature        rollout by rolling out in a selective manner.

These and other features and advantages of the present invention willbecome apparent from the following detailed description of illustrativeembodiments thereof, which is to be read in connection with theaccompanying drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram of an exemplary embodiment of a system, withinwhich one or more aspects of the invention can be implemented;

FIG. 2 is a functional block diagram illustrating an exemplary hybridfiber-coaxial (HFC) divisional network configuration, useful within thesystem of FIG. 1;

FIG. 3 is a functional block diagram illustrating one exemplary HFCcable network head-end configuration, useful within the system of FIG.1;

FIG. 4 is a functional block diagram illustrating one exemplary localservice node configuration useful within the system of FIG. 1;

FIG. 5 is a functional block diagram of a premises network, including anexemplary centralized customer premises equipment (CPE) unit,interfacing with a head end such as that of FIG. 3;

FIG. 6 is a functional block diagram of an exemplary centralized CPEunit, useful within the system of FIG. 1;

FIG. 7 is a block diagram of a computer system useful in connection withone or more aspects of the invention;

FIG. 8 is a functional block diagram illustrating an exemplary FTTHsystem, which is one exemplary system within which one or moreembodiments could be employed;

FIG. 9 is a functional block diagram of an exemplary centralized S-ONUCPE unit interfacing with the system of FIG. 8;

FIG. 10 is a block diagram of an exemplary system for video clientmanagement of video service feature flags for all or a subset of users,in accordance with an example embodiment;

FIG. 11 is a data flow sequence diagram of an exemplary system for videoclient management of video service feature flags for all or a subset ofusers, in accordance with an example embodiment;

FIG. 12 shows adjustment of a client user interface in accordance withfeature flags, according to an aspect of the invention; and

FIGS. 13A and 13B show exemplary logic that can be implemented on atargeted feature configuration flag server, according to an aspect ofthe invention.

DETAILED DESCRIPTION OF PREFERRED EMBODIMENTS

Purely by way of example and not limitation, some embodiments will beshown in the context of a cable multi-service operator (MSO) providingdata services as well as entertainment services. FIG. 1 shows anexemplary system 1000, according to an aspect of the invention. System1000 includes a regional data center (RDC) 1048 coupled to severalMarket Center Head Ends (MCHEs) 1096; each MCHE 1096 is in turn coupledto one or more divisions, represented by division head ends 150. In anon-limiting example, the MCHEs are coupled to the RDC 1048 via anetwork of switches and routers. One suitable example of network 1046 isa dense wavelength division multiplex (DWDM) network. The MCHEs can beemployed, for example, for large metropolitan area. In addition, theMCHE is connected to localized HEs 150 via high-speed routers 1091(“HER”=head end router) and a suitable network, which could, forexample, also utilize DWDM technology. Elements 1048, 1096 on network1046 may be operated, for example, by or on behalf of a cable MSO, andmay be interconnected with a global system of interconnected computernetworks that use the standardized Internet Protocol Suite(TCP/IP)(transfer control protocol/Internet protocol), commonly calledthe Internet 1002; for example, via router 1008. In one or morenon-limiting exemplary embodiments, router 1008 is a point-of-presence(“POP”) router; for example, of the kind available from JuniperNetworks, Inc., Sunnyvale, Calif., USA.

Head end routers 1091 are omitted from figures below to avoid clutter,and not all switches, routers, etc. associated with network 1046 areshown, also to avoid clutter.

RDC 1048 may include one or more provisioning servers (PS) 1050, one ormore Video Servers (VS) 1052, one or more content servers (CS) 1054, andone or more e-mail servers (ES) 1056. The same may be interconnected toone or more RDC routers (RR) 1060 by one or more multi-layer switches(MLS) 1058. RDC routers 1060 interconnect with network 1046.

A national data center (NDC) 1098 is provided in some instances; forexample, between router 1008 and Internet 1002. In one or moreembodiments, such an NDC may consolidate at least some functionalityfrom head ends (local and/or market center) and/or regional datacenters. For example, such an NDC might include one or more VOD servers;switched digital video (SDV) functionality; gateways to obtain content(e.g., program content) from various sources including cable feedsand/or satellite; and so on.

In some cases, there may be more than one national data center 1098(e.g., two) to provide redundancy. There can be multiple regional datacenters 1048. In some cases, MCHEs could be omitted and the local headends 150 coupled directly to the RDC 1048.

FIG. 2 is a functional block diagram illustrating an exemplarycontent-based (e.g., hybrid fiber-coaxial (HFC)) divisional networkconfiguration, useful within the system of FIG. 1. See, for example, USPatent Publication 2006/0130107 of Gonder et al., entitled “Method andapparatus for high bandwidth data transmission in content-basednetworks,” the complete disclosure of which is expressly incorporated byreference herein in its entirety for all purposes. The variouscomponents of the network 100 include (i) one or more data andapplication origination points 102; (ii) one or more applicationdistribution servers 104; (iii) one or more video-on-demand (VOD)servers 105, and (v) consumer premises equipment or customer premisesequipment (CPE). The distribution server(s) 104, VOD servers 105 andCPE(s) 106 are connected via a bearer (e.g., HFC) network 101. Servers104, 105 can be located in head end 150. A simple architecture is shownin FIG. 2 for illustrative brevity, although it will be recognized thatcomparable architectures with multiple origination points, distributionservers, VOD servers, and/or CPE devices (as well as different networktopologies) may be utilized consistent with embodiments of theinvention. For example, the head-end architecture of FIG. 3 (describedin greater detail below) may be used.

It should be noted that the exemplary CPE 106 is an integrated solutionincluding a cable modem (e.g., DOCSIS) and one or more wireless routers.Other embodiments could employ a two-box solution; i.e., separate cablemodem and routers suitably interconnected, which nevertheless, wheninterconnected, can provide equivalent functionality. Furthermore, FTTHnetworks can employ S-ONUs as CPE, as discussed elsewhere herein.

The data/application origination point 102 comprises any medium thatallows data and/or applications (such as a VOD-based or “Watch TV”application) to be transferred to a distribution server 104, forexample, over network 1102. This can include for example a third-partydata source, application vendor web site, compact disk read-only memory(CD-ROM), external network interface, mass storage device (e.g.,Redundant Arrays of Inexpensive Disks (RAID) system), etc. Suchtransference may be automatic, initiated upon the occurrence of one ormore specified events (such as the receipt of a request packet oracknowledgement (ACK)), performed manually, or accomplished in anynumber of other modes readily recognized by those of ordinary skill,given the teachings herein. For example, in one or more embodiments,network 1102 may correspond to network 1046 of FIG. 1, and the data andapplication origination point may be, for example, within NDC 1098, RDC1048, or on the Internet 1002. Head end 150, HFC network 101, and CPEs106 thus represent the divisions which were represented by division headends 150 in FIG. 1.

The application distribution server 104 comprises a computer systemwhere such applications can enter the network system. Distributionservers per se are well known in the networking arts, and accordinglynot described further herein.

The VOD server 105 comprises a computer system where on-demand contentcan be received from one or more of the aforementioned data sources 102and enter the network system. These servers may generate the contentlocally, or alternatively act as a gateway or intermediary from adistant source.

The CPE 106 includes any equipment in the “customers' premises” (orother appropriate locations) that can be accessed by the relevantupstream network components. Non-limiting examples of relevant upstreamnetwork components, in the context of the HFC network, include adistribution server 104 or a cable modem termination system 156(discussed below with regard to FIG. 3). The skilled artisan will befamiliar with other relevant upstream network components for other kindsof networks (e.g. FTTH) as discussed herein. Non-limiting examples ofCPE are set-top boxes, high-speed cable modems, and Advanced WirelessGateways (AWGs) for providing high bandwidth Internet access in premisessuch as homes and businesses. Reference is also made to the discussionof an exemplary FTTH network in connection with FIGS. 8 and 9.

Also included (for example, in head end 150) is a dynamic bandwidthallocation device (DBWAD) 1001 such as a global session resourcemanager, which is itself a non-limiting example of a session resourcemanager.

FIG. 3 is a functional block diagram illustrating one exemplary HFCcable network head-end configuration, useful within the system ofFIG. 1. As shown in FIG. 3, the head-end architecture 150 comprisestypical head-end components and services including billing module 152,subscriber management system (SMS) and CPE configuration managementmodule 3308, cable-modem termination system (CMTS) and out-of-band (OOB)system 156, as well as LAN(s) 158, 160 placing the various components indata communication with one another. In one or more embodiments, thereare multiple CMTSs. Each may be coupled to an HER 1091, for example.See, e.g., FIGS. 1 and 2 of co-assigned U.S. Pat. No. 7,792,963 ofinventors Gould and Danforth, entitled METHOD TO BLOCK UNAUTHORIZEDNETWORK TRAFFIC IN A CABLE DATA NETWORK, the complete disclosure ofwhich is expressly incorporated herein by reference in its entirety forall purposes.

It will be appreciated that while a bar or bus LAN topology isillustrated, any number of other arrangements (e.g., ring, star, etc.)may be used consistent with the invention. It will also be appreciatedthat the head-end configuration depicted in FIG. 3 is high-level,conceptual architecture and that each multi-service operator (MSO) mayhave multiple head-ends deployed using custom architectures.

The architecture 150 of FIG. 3 further includes amultiplexer/encrypter/modulator (MEM) 162 coupled to the HFC network 101adapted to “condition” content for transmission over the network. Thedistribution servers 104 are coupled to the LAN 160, which providesaccess to the MEM 162 and network 101 via one or more file servers 170.The VOD servers 105 are coupled to the LAN 158, although otherarchitectures may be employed (such as for example where the VOD serversare associated with a core switching device such as an 802.3z GigabitEthernet device; or the VOD servers could be coupled to LAN 160). Sinceinformation is typically carried across multiple channels, the head-endshould be adapted to acquire the information for the carried channelsfrom various sources. Typically, the channels being delivered from thehead-end 150 to the CPE 106 (“downstream”) are multiplexed together inthe head-end and sent to neighborhood hubs (refer to description of FIG.4) via a variety of interposed network components.

Content (e.g., audio, video, etc.) is provided in each downstream(in-band) channel associated with the relevant service group. (Note thatin the context of data communications, internet data is passed bothdownstream and upstream.) To communicate with the head-end orintermediary node (e.g., hub server), the CPE 106 may use theout-of-band (OOB) or DOCSIS® (Data Over Cable Service InterfaceSpecification) channels (registered mark of Cable TelevisionLaboratories, Inc., 400 Centennial Parkway Louisville Colo. 80027, USA)and associated protocols (e.g., DOCSIS 1.x, 2.0, 3.0, or 3.1). TheOpenCable™ Application Platform (OCAP) 1.0, 1.3.1, 2.0, 3.0 (andsubsequent) specification (Cable Television laboratories Inc.) providesfor exemplary networking protocols both downstream and upstream,although the invention is in no way limited to these approaches. Allversions of the DOCSIS and OCAP specifications are expresslyincorporated herein by reference in their entireties for all purposes.

Furthermore in this regard, DOCSIS is an internationaltelecommunications standard that permits the addition of high-speed datatransfer to an existing cable TV (CATV) system. It is employed by manycable television operators to provide Internet access (cable Internet)over their existing hybrid fiber-coaxial (HFC) infrastructure. Use ofDOCSIS to transmit data on an HFC system is one non-limiting exemplaryapplication context for one or more embodiments. However, one or moreembodiments are generally applicable to IP transport of data, regardlessof what kind of functionality is employed. It is also worth noting thatthe use of DOCSIS Provisioning of EPON (Ethernet over Passive OpticalNetwork) or “DPoE” (Specifications available from CableLabs, Louisville,Colo., USA) enables the transmission of high-speed data over PONs usingDOCSIS back-office systems and processes.

It will also be recognized that multiple servers (broadcast, VOD, orotherwise) can be used, and disposed at two or more different locationsif desired, such as being part of different server “farms”. Thesemultiple servers can be used to feed one service group, or alternativelydifferent service groups. In a simple architecture, a single server isused to feed one or more service groups. In another variant, multipleservers located at the same location are used to feed one or moreservice groups. In yet another variant, multiple servers disposed atdifferent location are used to feed one or more service groups.

In some instances, material may also be obtained from a satellite feed1108; such material is demodulated and decrypted in block 1106 and fedto block 162. Conditional access system 157 may be provided for accesscontrol purposes. Network management system 1110 may provide appropriatemanagement functions. Note also that signals from MEM 162 and upstreamsignals from network 101 that have been demodulated and split in block1112 are fed to CMTS and OOB system 156.

Also included in FIG. 3 are a global session resource manager (GSRM)3302, a Mystro Application Server 104A, and a business management system154, all of which are coupled to LAN 158. GSRM 3302 is one specific formof a DBWAD 1001 and is a non-limiting example of a session resourcemanager.

An ISP DNS server could be located in the head-end as shown at 3303, butit can also be located in a variety of other places. One or more DynamicHost Configuration Protocol (DHCP) server(s) 3304 can also be locatedwhere shown or in different locations.

As shown in FIG. 4, the network 101 of FIGS. 2 and 3 comprises afiber/coax arrangement wherein the output of the MEM 162 of FIG. 3 istransferred to the optical domain (such as via an optical transceiver177 at the head-end 150 or further downstream). The optical domainsignals are then distributed over a fiber network to a fiber node 178,which further distributes the signals over a distribution network 180(typically coax) to a plurality of local servicing nodes 182. Thisprovides an effective 1-to-N expansion of the network at the localservice end. Each node 182 services a number of CPEs 106. Furtherreference may be had to US Patent Publication 2007/0217436 of Markley etal., entitled “Methods and apparatus for centralized content and datadelivery,” the complete disclosure of which is expressly incorporatedherein by reference in its entirety for all purposes. In one or moreembodiments, the CPE 106 includes a cable modem, such as aDOCSIS-compliant cable modem (DCCM). Please note that the number n ofCPE 106 per node 182 may be different than the number n of nodes 182,and that different nodes may service different numbers n of CPE.

Certain additional aspects of video or other content delivery will nowbe discussed for completeness, it being understood that embodiments ofthe invention have broad applicability to TCP/IP network connectivityfor delivery of messages and/or content.

Again, delivery of data over a video (or other) content network is butone non-limiting example of a context where one or more embodimentscould be implemented. US Patent Publication 2003-0056217 of Paul D.Brooks, entitled “Technique for Effectively Providing Program Materialin a Cable Television System,” the complete disclosure of which isexpressly incorporated herein by reference for all purposes, describesone exemplary broadcast switched digital architecture, although it willbe recognized by those of ordinary skill that other approaches andarchitectures may be substituted. In a cable television system inaccordance with the Brooks invention, program materials are madeavailable to subscribers in a neighborhood on an as-needed basis.Specifically, when a subscriber at a set-top terminal selects a programchannel to watch, the selection request is transmitted to a head end ofthe system. In response to such a request, a controller in the head enddetermines whether the material of the selected program channel has beenmade available to the neighborhood. If it has been made available, thecontroller identifies to the set-top terminal the carrier which iscarrying the requested program material, and to which the set-topterminal tunes to obtain the requested program material. Otherwise, thecontroller assigns an unused carrier to carry the requested programmaterial, and informs the set-top terminal of the identity of the newlyassigned carrier. The controller also retires those carriers assignedfor the program channels which are no longer watched by the subscribersin the neighborhood. Note that reference is made herein, for brevity, tofeatures of the “Brooks invention”—it should be understood that noinference should be drawn that such features are necessarily present inall claimed embodiments of Brooks. The Brooks invention is directed to atechnique for utilizing limited network bandwidth to distribute programmaterials to subscribers in a community access television (CATV) system.In accordance with the Brooks invention, the CATV system makes availableto subscribers selected program channels, as opposed to all of theprogram channels furnished by the system as in prior art. In the BrooksCATV system, the program channels are provided on an as needed basis,and are selected to serve the subscribers in the same neighborhoodrequesting those channels.

US Patent Publication 2010-0313236 of Albert Straub, entitled“TECHNIQUES FOR UPGRADING SOFTWARE IN A VIDEO CONTENT NETWORK,” thecomplete disclosure of which is expressly incorporated herein byreference for all purposes, provides additional details on theaforementioned dynamic bandwidth allocation device 1001.

US Patent Publication 2009-0248794 of William L. Helms, entitled “SYSTEMAND METHOD FOR CONTENT SHARING,” the complete disclosure of which isexpressly incorporated herein by reference for all purposes, providesadditional details on CPE in the form of a converged premises gatewaydevice. Related aspects are also disclosed in US Patent Publication2007-0217436 of Markley et al, entitled “METHODS AND APPARATUS FORCENTRALIZED CONTENT AND DATA DELIVERY,” the complete disclosure of whichis expressly incorporated herein by reference for all purposes.

Reference should now be had to FIG. 5, which presents a block diagram ofa premises network interfacing with a head end of an MSO or the like,providing Internet access. An exemplary advanced wireless gatewaycomprising CPE 106 is depicted as well. It is to be emphasized that thespecific form of CPE 106 shown in FIGS. 5 and 6 is exemplary andnon-limiting, and shows a number of optional features. Many other typesof CPE can be employed in one or more embodiments; for example, a cablemodem, DSL modem, and the like. The CPE can also be a Service OpticalNetwork Unit (S-ONU) for FTTH deployment—see FIGS. 8 and 9 andaccompanying text.

CPE 106 includes an advanced wireless gateway which connects to a headend 150 or other hub of a network, such as a video content network of anMSO or the like. The head end is coupled also to an internet (e.g., theInternet) 208 which is located external to the head end 150, such as viaan Internet (IP) backbone or gateway (not shown).

The head end is in the illustrated embodiment coupled to multiplehouseholds or other premises, including the exemplary illustratedhousehold 240. In particular, the head end (for example, a cable modemtermination system 156 thereof) is coupled via the aforementioned HFCnetwork and local coaxial cable or fiber drop to the premises, includingthe consumer premises equipment (CPE) 106. The exemplary CPE 106 is insignal communication with any number of different devices including,e.g., a wired telephony unit 222, a Wi-Fi or other wireless-enabledphone 224, a Wi-Fi or other wireless-enabled laptop 226, a sessioninitiation protocol (SIP) phone, an H.323 terminal or gateway, etc.Additionally, the CPE 106 is also coupled to a digital video recorder(DVR) 228 (e.g., over coax), in turn coupled to television 234 via awired or wireless interface (e.g., cabling, PAN or 802.15 UWB micro-net,etc.). CPE 106 is also in communication with a network (here, anEthernet network compliant with IEEE Std. 802.3, although any number ofother network protocols and topologies could be used) on which is apersonal computer (PC) 232.

Other non-limiting exemplary devices that CPE 106 may communicate withinclude a printer 294; for example, over a universal plug and play(UPnP) interface, and/or a game console 292; for example, over amultimedia over coax alliance (MoCA) interface.

In some instances, CPE 106 is also in signal communication with one ormore roaming devices, generally represented by block 290.

A “home LAN” (HLAN) is created in the exemplary embodiment, which mayinclude for example the network formed over the installed coaxialcabling in the premises, the Wi-Fi network, and so forth.

During operation, the CPE 106 exchanges signals with the head end overthe interposed coax (and/or other, e.g., fiber) bearer medium. Thesignals include e.g., Internet traffic (IPv4 or IPv6), digitalprogramming and other digital signaling or content such as digital(packet-based; e.g., VoIP) telephone service. The CPE 106 then exchangesthis digital information after demodulation and any decryption (and anydemultiplexing) to the particular system(s) to which it is directed oraddressed. For example, in one embodiment, a MAC address or IP addresscan be used as the basis of directing traffic within the client-sideenvironment 240.

Any number of different data flows may occur within the network depictedin FIG. 5. For example, the CPE 106 may exchange digital telephonesignals from the head end which are further exchanged with the telephoneunit 222, the Wi-Fi phone 224, or one or more roaming devices 290. Thedigital telephone signals may be IP-based such as Voice-over-IP (VoIP),or may utilize another protocol or transport mechanism. The well-knownsession initiation protocol (SIP) may be used, for example, in thecontext of a “SIP phone” for making multi-media calls. The network mayalso interface with a cellular or other wireless system, such as forexample a 3G IMS (IP multimedia subsystem) system, in order to providemultimedia calls between a user or consumer in the household domain 240(e.g., using a SIP phone or H.323 terminal) and a mobile 3G telephone orpersonal media device (PMD) user via that user's radio access network(RAN).

The CPE 106 may also exchange Internet traffic (e.g., TCP/IP and otherpackets) with the head end 150 which is further exchanged with the Wi-Filaptop 226, the PC 232, one or more roaming devices 290, or otherdevice. CPE 106 may also receive digital programming that is forwardedto the DVR 228 or to the television 234. Programming requests and othercontrol information may be received by the CPE 106 and forwarded to thehead end as well for appropriate handling.

FIG. 6 is a block diagram of one exemplary embodiment of the CPE 106 ofFIG. 5. The exemplary CPE 106 includes an RF front end 301, Wi-Fiinterface 302, video interface 316, “Plug n' Play” (PnP) interface 318(for example, a UPnP interface) and Ethernet interface 304, eachdirectly or indirectly coupled to a bus 312. In some cases, Wi-Fiinterface 302 comprises a single wireless access point (WAP) runningmultiple (“m”) service set identifiers (SSIDs). In some cases, multipleSSIDs, which could represent different applications, are served from acommon WAP. For example, SSID 1 is for the home user, while SSID 2 maybe for a managed security service, SSID 3 may be a managed homenetworking service, SSID 4 may be a hot spot, and so on. Each of theseis on a separate IP subnetwork for security, accounting, and policyreasons. The microprocessor 306, storage unit 308, plain old telephoneservice (POTS)/public switched telephone network (PSTN) interface 314,and memory unit 310 are also coupled to the exemplary bus 312, as is asuitable MoCA interface 391. The memory unit 310 typically comprises arandom-access memory (RAM) and storage unit 308 typically comprises ahard disk drive, an optical drive (e.g., CD-ROM or DVD), NAND flashmemory, RAID (redundant array of inexpensive disks) configuration, orsome combination thereof.

The illustrated CPE 106 can assume literally any discrete form factor,including those adapted for desktop, floor-standing, or wall-mounteduse, or alternatively may be integrated in whole or part (e.g., on acommon functional basis) with other devices if desired.

Again, it is to be emphasized that every embodiment need not necessarilyhave all the elements shown in FIG. 6—as noted, the specific form of CPE106 shown in FIGS. 5 and 6 is exemplary and non-limiting, and shows anumber of optional features. Yet again, many other types of CPE can beemployed in one or more embodiments; for example, a cable modem, DSLmodem, and the like.

It will be recognized that while a linear or centralized busarchitecture is shown as the basis of the exemplary embodiment of FIG.6, other bus architectures and topologies may be used. For example, adistributed or multi-stage bus architecture may be employed. Similarly,a “fabric” or other mechanism (e.g., crossbar switch, RAPIDIO interface,non-blocking matrix, TDMA or multiplexed system, etc.) may be used asthe basis of at least some of the internal bus communications within thedevice. Furthermore, many if not all of the foregoing functions may beintegrated into one or more integrated circuit (IC) devices in the formof an ASIC or “system-on-a-chip” (SoC). Myriad other architectures wellknown to those in the data processing and computer arts may accordinglybe employed.

Yet again, it will also be recognized that the CPE configuration shownis essentially for illustrative purposes, and various otherconfigurations of the CPE 106 are consistent with other embodiments ofthe invention. For example, the CPE 106 in FIG. 6 may not include all ofthe elements shown, and/or may include additional elements andinterfaces such as for example an interface for the HomePlug A/Vstandard which transmits digital data over power lines, a PAN (e.g.,802.15), Bluetooth, or other short-range wireless interface forlocalized data communication, etc.

A suitable number of standard 10/100/1000 Base T Ethernet ports for thepurpose of a Home LAN connection are provided in the exemplary device ofFIG. 6; however, it will be appreciated that other rates (e.g., GigabitEthernet or 10-Gig-E) and local networking protocols (e.g., MoCA, USB,etc.) may be used. These interfaces may be serviced via a WLANinterface, wired RJ-45 ports, or otherwise. The CPE 106 can also includea plurality of RJ-11 ports for telephony interface, as well as aplurality of USB (e.g., USB 2.0) ports, and IEEE-1394 (Firewire) ports.S-video and other signal interfaces may also be provided if desired.

During operation of the CPE 106, software located in the storage unit308 is run on the microprocessor 306 using the memory unit 310 (e.g., aprogram memory within or external to the microprocessor). The softwarecontrols the operation of the other components of the system, andprovides various other functions within the CPE. Other systemsoftware/firmware may also be externally reprogrammed, such as using adownload and reprogramming of the contents of the flash memory,replacement of files on the storage device or within other non-volatilestorage, etc. This allows for remote reprogramming or reconfiguration ofthe CPE 106 by the MSO or other network agent.

It should be noted that some embodiments provide a cloud-based userinterface, wherein CPE 106 accesses a user interface on a server in thecloud, such as in NDC 1098.

The RF front end 301 of the exemplary embodiment comprises a cable modemof the type known in the art. In some cases, the CPE just includes thecable modem and omits the optional features. Content or data normallystreamed over the cable modem can be received and distributed by the CPE106, such as for example packetized video (e.g., IPTV). The digital dataexchanged using RF front end 301 includes IP or other packetizedprotocol traffic that provides access to internet service. As is wellknown in cable modem technology, such data may be streamed over one ormore dedicated QAMs resident on the HFC bearer medium, or evenmultiplexed or otherwise combined with QAMs allocated for contentdelivery, etc. The packetized (e.g., IP) traffic received by the CPE 106may then be exchanged with other digital systems in the localenvironment 240 (or outside this environment by way of a gateway orportal) via, e.g. the Wi-Fi interface 302, Ethernet interface 304 orplug-and-play (PnP) interface 318.

Additionally, the RF front end 301 modulates, encrypts/multiplexes asrequired, and transmits digital information for receipt by upstreamentities such as the CMTS or a network server. Digital data transmittedvia the RF front end 301 may include, for example, MPEG-2 encodedprogramming data that is forwarded to a television monitor via the videointerface 316. Programming data may also be stored on the CPE storageunit 308 for later distribution by way of the video interface 316, orusing the Wi-Fi interface 302, Ethernet interface 304, Firewire (IEEEStd. 1394), USB/USB2, or any number of other such options.

Other devices such as portable music players (e.g., MP3 audio players)may be coupled to the CPE 106 via any number of different interfaces,and music and other media files downloaded for portable use and viewing.

In some instances, the CPE 106 includes a DOCSIS cable modem fordelivery of traditional broadband Internet services. This connection canbe shared by all Internet devices in the premises 240; e.g. Internetprotocol television (IPTV) devices, PCs, laptops, etc., as well as byroaming devices 290. In addition, the CPE 106 can be remotely managed(such as from the head end 150, or another remote network agent) tosupport appropriate IP services. Some embodiments could utilize acloud-based user interface, wherein CPE 106 accesses a user interface ona server in the cloud, such as in NDC 1098.

In some instances, the CPE 106 also creates a home Local Area Network(LAN) utilizing the existing coaxial cable in the home. For example, anEthernet-over-coax based technology allows services to be delivered toother devices in the home utilizing a frequency outside (e.g., above)the traditional cable service delivery frequencies. For example,frequencies on the order of 1150 MHz could be used to deliver data andapplications to other devices in the home such as PCs, PMDs, mediaextenders and set-top boxes. The coaxial network is merely the bearer;devices on the network utilize Ethernet or other comparable networkingprotocols over this bearer.

The exemplary CPE 106 shown in FIGS. 5 and 6 acts as a Wi-Fi accesspoint (AP), thereby allowing Wi-Fi enabled devices to connect to thehome network and access Internet, media, and other resources on thenetwork. This functionality can be omitted in one or more embodiments.

In one embodiment, Wi-Fi interface 302 comprises a single wirelessaccess point (WAP) running multiple (“m”) service set identifiers(SSIDs). One or more SSIDs can be set aside for the home network whileone or more SSIDs can be set aside for roaming devices 290.

A premises gateway software management package (application) is alsoprovided to control, configure, monitor and provision the CPE 106 fromthe cable head-end 150 or other remote network node via the cable modem(DOCSIS) interface. This control allows a remote user to configure andmonitor the CPE 106 and home network. Yet again, it should be noted thatsome embodiments could employ a cloud-based user interface, wherein CPE106 accesses a user interface on a server in the cloud, such as in NDC1098.

The MoCA interface 391 can be configured, for example, in accordancewith the MoCA 1.0, 1.1, or 2.0 specifications.

As discussed above, the optional Wi-Fi wireless interface 302 is, insome instances, also configured to provide a plurality of unique serviceset identifiers (SSIDs) simultaneously. These SSIDs are configurable(locally or remotely), such as via a web page.

As noted, there are also fiber networks for fiber to the home (FTTH)deployments (also known as fiber to the premises or FTTP), where the CPEis a Service ONU (S-ONU; ONU=optical network unit). Referring now toFIG. 8, L3 network 802 generally represents the elements in FIG. 1upstream of the head ends 150, while head end 804, including accessrouter 806, is an alternative form of head end that can be used in lieuof or in addition to head ends 150 in one or more embodiments. Head end804 is suitable for FTTH implementations. Access router 806 of head end804 is coupled to optical line terminal 812 in primary distributioncabinet 810 via dense wavelength division multiplexing (DWDM) network808. Single fiber coupling 814 is then provided to a 1:64 splitter 818in secondary distribution cabinet 816 which provides a 64:1 expansion tosixty-four S-ONUs 822-1 through 822-64 (in multiple premises) viasixty-four single fibers 820-1 through 820-64, it being understood thata different ratio splitter could be used in other embodiments and/orthat not all of the 64 (or other number of) outlet ports are necessarilyconnected to an S-ONU.

Giving attention now to FIG. 9, wherein elements similar to those inFIG. 8 have been given the same reference number, access router 806 isprovided with multiple ten-Gigabit Ethernet ports 999 and is coupled toOLT 812 via L3 (layer 3) link aggregation group (LAG) 997. OLT 812 caninclude an L3 IP block for data and video, and another L3 IP block forvoice, for example. In a non-limiting example, S-ONU 822 includes a 10Gbps bi-directional optical subassembly (BOSA) on-board transceiver 993with a 10G connection to system-on-chip (SoC) 991. SoC 991 is coupled toa 10 Gigabit Ethernet RJ45 port 979, to which a high-speed data gateway977 with Wi-Fi capability is connected via category 5E cable. Gateway977 is coupled to one or more set-top boxes 975 via category 5e, andeffectively serves as a wide area network (WAN) to local area network(LAN) gateway. Wireless and/or wired connections can be provided todevices such as laptops 971, televisions 973, and the like, in a knownmanner. Appropriate telephonic capability can be provided. In anon-limiting example, residential customers are provided with aninternal integrated voice gateway (I-ATA or internal analog telephoneadapter) 983 coupled to SoC 991, with two RJ11 voice ports 981 to whichup to two analog telephones 969 can be connected. Furthermore, in anon-limiting example, business customers are further provided with a 1Gigabit Ethernet RJ45 port 989 coupled to SoC 991, to which switch 987is coupled via Category 5e cable. Switch 987 provides connectivity for adesired number n (typically more than two) of analog telephones 967-1through 967-n, suitable for the needs of the business, via externalanalog telephone adapters (ATAs) 985-1 through 985-n. The parameter “n”in FIG. 9 is not necessarily the same as the parameter “n” in otherfigures, but rather generally represents a desired number of units.Connection 995 can be, for example, via SMF (single-mode optical fiber).

In addition to “broadcast” and/or “on-demand” content (e.g., videoprogramming), the systems of FIGS. 1-6, 8, and 9 can optionally alsodeliver Internet data services using the Internet protocol (IP),although other protocols and transport mechanisms of the type well knownin the digital communication art may be substituted. In the systems ofFIGS. 1-6, the IP packets are typically transmitted on RF channels thatare different that the RF channels used for the broadcast video andaudio programming, although this is not a requirement. The CPE 106 areeach configured to monitor the particular assigned RF channel (such asvia a port or socket ID/address, or other such mechanism) for IP packetsintended for the subscriber premises/address that they serve.

Referring to FIGS. 10 and 11, as noted, video clients 1201 often callinto back-end systems 1207 to obtain the data they need to displayprogram guide and on-demand menu pages. The back-end systems typicallyhave to manage feature flags so as not to return new features to clientsthat are not expecting those features. Usually, there is a carefulback-end/front-end release coordination, allowing for a release that allusers obtain at the same time. One or more embodiments advantageouslyprovide video clients 1201 a mechanism to instruct a back-end service(e.g. server 1207 and database 1211) to enable a feature flag for asubset of the total population, allowing for canary rollouts of features(slow increase in users over time; the small subset of users acts as a“canary in a coal mine” to warn of any issues with the feature prior towidespread implementation), A/B experimentation, and the like. A/Btesting provides, for example, an experimentation method to prove that afeature is useful to customers of an MSO or the like. For example, anexperiment could utilize 10% of all customers. One-half off the 10%, or5%, would be in the control group and the other one-half of them,another 5% of the total, would be in a variant group (there can bemultiple variants). The control group does not get the feature; thevariant group does get the feature. Analytics can then be run on onlythose accounts to see if behavior of the users with the enabledfeature(s) is different after the feature(s) is/are enabled. Theexperiment can be run for a predetermined amount of time.

One or more embodiments enable a client 1201 to use a Targeted FeatureFlag Config server 1203 to activate features on back-end systems.Embodiments can be configured, for example, to manage and/or customizeflags for all users and/or a subset of users.

Client 1201 can correspond, for example, to end devices such as a smartphone 224; television 234, 973; game console 292; laptop 226, 971; PC232, a set-top box 975; and the like. Targeted Feature Flag Configserver 1203 can be located, for example, in a national data center 1098;a regional data center 1048; a head end 150; or in a cloud provideraccessed via Internet 1002 (e.g., Amazon Wes Services (AWS) CloudComputing Services available from Amazon.com, Inc. Seattle, Wash., USAor Google Cloud Platform Cloud Computing Services available from Google,Inc., Mountain View, Calif., USA). Back end server 1207 can be located,for example, in a national data center 1098; a regional data center1048; a head end 150; or in a cloud provider accessed via Internet 1002.Database 1211 can be collocated with server 1207 or located on a networkaccessible to server 1207. Servers 1203 and 1207 can each be implementedas one or more physical and/or virtual servers. As will be appreciatedby the skilled artisan, virtual servers are implemented on underlyinghardware servers using, for example, a hypervisor or the like. Theclient 1201, server 1203, and server 1207 can communicate, for example,as explained with respect to FIGS. 1-9. Client 1201 can, but need not,be in a customer premises; it could roam and connect to the Internet viawired or wireless connection (e.g. Wi-Fi, LAN, cellular network) or thelike.

One or more embodiments employ a back-end system including aclient-facing set of services responsible for page-by-page navigation,returning the content displayed on the page, determining the layout ofthe page, and determining what navigation actions can be taken from thispage. A non-limiting example of a possible goal of this type of designis to put all of the business logic (e.g. complex business logic that isshared across devices) in a back-end system and put only viewinformation on the front-end client, allowing for the quick roll-out offeatures and bug fixes across a multitude of clients. Other embodimentscould distribute the functionality differently; for example, thebusiness logic could be split 50/50 between the back-end system and theclient. In some instances, it may be quite desirable for the client tobe completely “dumb”; i.e., the backend would perform all business logicand the client just knows how to display data provided by the backend.This is because backends tend to have faster release cycles, morecompute power, and the centralization of functionality makes onboardingnew clients easier. Again, however, this is a non-limiting example.

Many new features can be developed on this back-end platform, anddisplayed on the front-end platform, as time goes on. When new featuresare developed, it may be desirable to deploy to employees first, then toa subset of customers, then to all customers. Another use case is thedisabling of features from the client. Suppose the default back-endservice behavior is to enable a feature for all devices and accounts.Further suppose that a bug is found only on a single device, or a groupof users with a common configuration. One or more embodiments can beused to disable the broken functionality on that device or the accountsof that group of users. In another aspect, consider a call center thatreceives a customer complaint that the customer does not like some newfeature or that some new feature is broken. One or more embodiments canbe used to disable the functionality for that one customer.

In one or more embodiments, the back-end servers, such as 1207, haveprofiles, defining a list of feature flags, for each version of eachclient. These feature flags represent the default state, generally inthe ‘off’ position. In one or more embodiments, for each client-facingAPI, the back-end servers define a new query param (see discussion of1225 below) allowing clients to override the ‘default’ feature flagvalue. One or more embodiments include a Targeted-Feature-Flag-Deliverysystem which the client 1201 downloads at initialization time fromserver 1203. This system provides the clients with a list of featureflags if it determines they are part of a target group. Target groupscan be defined, for example, as a whitelist of IP addresses or groups inexperiment variants. A target group can be employed to split out a listof accounts for special functionality using a wide variety of criteria;e.g., Employee Field Trials, Alpha/Beta testers, demoing groups, testaccounts, customers who purchase specific package levels, customers whoopt into or opt out of a feature, experiment groups, and the like. Oneof the fields associated with the targeted feature flag system is aback-end feature flag enablement. When these flags are set, the clientpasses these flags to the back-end using the pre-defined query param.One pertinent aspect is the activation of back-end feature flags fromthe front-end (some architectures can have experiments and featurerollouts initiated from the front-end). Another pertinent aspect of oneor more embodiments is the ability to roll out back-end features to asubset of customers. By way of further comment, a common goal of backendsystems is to be completely stateless. This means the backend knowsnothing about the user or account or the user's previous interactionwith the system. All state information has to be passed from the clientto the server with the request. As such, the control of feature flags ona per user or account level “belongs” with the client as in one or moreembodiments, clients are always stateful. Of course, other embodimentscan be configured differently.

One or more embodiments advantageously permit activation of back-endfeature flags from the front end; for example, it is possible to rollout back-end features to a subset of customers. The skilled artisan willbe familiar with feature flags per se. As will be appreciated by theskilled artisan, feature flags (also known as feature toggles or featureswitches) are a software development technique that turns certainfunctionality on and off during runtime, without deploying new code. Oneor more embodiments include account-level enabling of feature flags. Oneor more embodiments allow client teams and client organizations to beable to interface with the full back-end feature set though clientinterfaces. Backend services, such as a navigation server, tend to havemany feature flags. In one or more embodiments, the client now has theability to enable any combination of feature flags, on the backendsystem, for any single account or group of accounts using any of thepreviously described methodologies for selecting accounts (Canary,Experiment, etc.).

One or more embodiments can be used, for example, in the case of a thickservice and a thin client, where the thick service will implement all(can be less than all in other embodiments) the new features; e.g. a newsearch feature. Suppose it is not desired to deploy the new searchfeature on all clients right away. Suppose that it is desired to employthe new search feature on only on a subset of clients and on only on asubset of accounts within a given client type.

Currently, there is no way for a client, in conjunction with a back-endsystem, to enable and disable certain functions per account level. Oneor more embodiments allow, when ready to deploy, one or more of: (i)listing individual accounts; (ii) turning on back-end features for alist of white-listed accounts; and (iii) running AB testing where, say,15% of the accounts are used for an experiment (say, 5% of accounts (⅓of the tested accounts) get a certain feature A, 5% of accounts (another⅓ of the tested accounts) get a feature B, and another 5% of accounts(final ⅓ of the tested accounts) are a control group. Alternatively, orin addition, one or more embodiments also allow so-called “canaryrollouts” where 1% of the customer base obtains a feature and thepercentage is increased slowly over time; say, 5%, 10%, 15% . . . 100%—aslow rollout. Time intervals can be chosen by the operations team, forexample, using suitable heuristics (e.g. dependent on how risky thechange is to the business). In a non-limiting example, one-week betweenramp-ups is used. Furthermore, alternatively, or in addition, one ormore embodiments also allow enabling feature(s) just for a singleengineer on a system so system operators can carry out development;e.g., without having to turn the feature(s) on globally for everyone.For example, the feature(s) may just be enabled for a development lab.

One or more embodiments advantageously provide the ability to switchback-end features on and off on a per-account level.

FIG. 10 is a block diagram of an exemplary system for video clientmanagement of video service feature flags, in accordance with an exampleembodiment. In the type of exemplary organization of components depictedin FIG. 10, the ability to turn features on and off from an accountlevel is carried out within a client tier. Elements 1201, 1203 canoptionally be located in a client tier that back-end systems do not haveany interaction with. More specifically, in a non-limiting example, 1201is the client device (phone, set-top box, consumer electronics (CE)device), while 1203 is an account configuration targeting web servicethat is closely integrated with the client-tier and has no interactionwith backend components, only clients. Other approaches can be employedin other embodiments.

Client X 1201 can include, for example, a remote control; a set-top box(e.g., 975 or connected to/included in 106); smart cell phone 224; orthe like. The cell phone can, for example, act as a standalone device (afull guide with viewing capabilities) and can also act as a companiondevice (a remote that allows the user to control the user's home set-topbox). In the former capacity, the phone can control cloud-base DVRfunctionality. Client X 1201, as part of its start-up process (forexample), calls into a targeted feature flag config (configuration)server 1203 that provides a Targeted-Feature-Flag-Delivery service.Client 1201 asks server 1203 for a list of the feature flags to beoverridden on back-end server A 1207. This request will include, forexample, account information and device IDs; a non-limiting example isshown at 1202. The targeted feature flag config server 1203 can thenlook up what features should be enabled (disabled status overridden) forthe account associated with Client X 1201 (e.g. “Account Y”). Thetargeted feature flag config server 1203 enables, for example,whitelisting, experimentation, and the like. In one or more embodiments,Client X makes a RESTFUL API call 1202 to the targeted feature flagconfig server 1203. The targeted feature flag config server 1203resides, for example, in the cloud.

While the Client X 1201 obtains the list of feature flags that it isgoing to override, Back End Server A 1207 already has, for Client TypeX, a set of default values for feature flags. For example, supposeClient X is an Android® device (registered mark of GOOGLE LLC MOUNTAINVIEW Calif. USA). Back End Server A 1207 already has a list of featureflags for Android® Device Version 5, e.g. Suppose all the features areturned off, and that Back-End Server A has just implemented a new searchfeature and by default it has this new feature turned off for Android®Version 5. Most Android® Version 5 clients that call in will get a valueof “turned off” and will not have the feature turned on in the back-endsystem. However, in the example, Client X, which is an Android® Version5 client, is part of an account, white list, or experiment that getsback a feature flag from the targeted feature flag config server 1203which it passes to the Back End Server A 1207 in message 1205, causingBack End Server A to override the default for Client X associated withAccount Y, as seen at 1209. The default flags can be stored, forexample, in a profile in database 1211.

FIG. 11 is a data flow sequence diagram of an exemplary system for videoclient management of video service feature flags, in accordance with anexample embodiment. Client X 1201 (e.g. via an “app” in memory 730—seediscussion of FIG. 7 elsewhere herein), during its start-up process (forexample), and/or at some interval, calls into the targeted feature flagconfig server 1203 to obtain the list of feature overrides to make onthe back-end server A 1207. This call can be, for example, via an APIand is shown at 1221 in FIG. 11 (1202 in FIG. 10 and 1221 in FIG. 11 areboth non-limiting examples). Note that a set-top terminal is typicallyassociated with a long-lived process which should call in both onstart-up and again at periodic intervals, while shorter-lived processesmight call in only at start-up. The targeted feature flag config servereffectively determines “this is Account Y and it is part of a whitelistgroup or part of an experiment so we will override feature flags onback-end server A for this client.” The response with overrides is shownat 1223. As seen at 1225 in FIG. 11 (1225 in FIG. 11 and 1205 in FIG. 10are both non-limiting examples), Client X 1201 then passes those featureflag values into back end server A 1207 as Query Params, HTTP Headers,via an HTTP POST body (e.g. client 1201 does the post and passes it as apost body) or the like.

Back end server A 1207 obtains those feature flag override values andlooks up the default values for Client X (in the feature flag database“FeatureFlagDB” 1211—the query is seen at 1227 and the response at1229). Back end server A then overrides the default feature flag valuesfrom the database 1211, as seen at 1231, as per what was passed by theclient in message 1225. The back-end server 1207 now has a plurality offeature flags associated with client 1201—some of them are defaultvalues and some of them are overridden values. As seen at 1233, 1235,Back End Server A 1207 fulfills the request; when Back End Server A 1207reaches the code that deals with a new feature, the feature flag willindicate to enable that new feature because the client 1201 enabled itthrough the query param 1225; i.e., the updated feature flag profile forclient 1201 includes default values from database 1211 for features notoverridden and includes the overridden values for features that wereoverridden.

In one or more embodiments, Client X 1201 “knows” that certain defaultfeature flags should be overridden because client 1201 calls targetedfeature flag config server 1203 with an indication of its account ID anddevice ID. The targeted feature flag config server 1203 includes logicfor whitelisting, experimentation, canary rollout, and the like. Inexecuting the logic, the targeted feature flag config server 1203 “sees”that the client 1201 is in, e.g., a (whitelist) group that should havecertain feature flag overrides. There is logic on the targeted featureflag config server 1203 that stores certain overrides for each account.The client 1201 communicates with the back-end server 1207, whichobtains the default profile from the database 1211; server 1207 thenselectively overrides the profile based on the information from thetargeted feature flag config server 1203 that was relayed by the client1201.

Thus, one or more embodiments advantageously allow the client 1201 tocontrol the enablement and disablement of the feature flags on theback-end server 1207. The client 1201 sends a communication to theback-end server 1207 based on the information it received from thetargeted feature flag config server 1203.

Consider a case where Client App X 1201 has a feature such as “thebutton is blue.” It is desired to have a new feature to make the buttonred. The client itself can have features and feature flags. While theclient can call into the feature flag config server 1203 to changefeatures on the client, one or more embodiments allow the client tocontrol the back-end features. One or more embodiments are useful, forexample, in a thick server thin client environment (e.g., server hasmore functionality than the client—for example, the client has minimalfunctionality, and the server has most of the functionality. As afurther specific example, in some cases, clients are responsible fordisplaying the graphics on the screen (button locations, colors, fonts,etc.). Backend services are responsible for the business functionality(what functional activities happen when a button is pressed, atext-field is populated, or a new page is loaded). Furthermore in thisregard, in one or more embodiments, a goal of back-end services is toimplement shared functionality. For example, suppose an MSO supportstwelve different types of clients (e.g., smart phones, remote-controlledtelevisions, . . . ). It is desirable for common or shared functionalityto be implemented in the back end (e.g., RDVR (remote DVR), navigationof program guides, search functionality, and the like). Functionality onthe client is preferably limited to client-specific logic, such as howto render material provided to the client by the back-end.

Thus, one or more embodiments enable activation of back-end (e.g. onserver 1207) feature flags from the front end (e.g. via client 1201);provide the ability to roll out back-end features to a subset ofcustomers; and the like. For example, the targeted feature flag configserver 1203 can have logic in it to, for example, only enable a featurefor 5% of the customers. The targeted feature flag config server canhave the ability to whitelist accounts. Say, a certain 250 accounts areto have the feature flag, or the feature flag is to be assigned bypercentage. For example, in the latter case, 5% of customers arerandomly given a feature flag. One or more embodiments also permitrunning experiments with variants—say, 5% of customers get the Variant Afeature flag, 5% of customers get the Variant B feature flag, 5% serveas a control, and so on. One advantage of one or more embodiments isthat the client can now control back-end feature enablement. The clientcan use logic on the targeted feature flag config server to push outchanges/enable features on the back-end server.

One or more embodiments advantageously allow account-level targeting ofbackend features. There are several ways this can be utilized,including, for example, canary release of the feature (by % of customersor by market or device), experimentation on the feature (A/B Testing),Whitelisting/Blacklisting of the feature, as a mechanism for enablingthe feature for all customers, and the like.

Recapitulation

Given the discussion thus far, it will be appreciated that, in generalterms, an exemplary method, according to an aspect of the invention,includes the step of, at a video content network client 1201, obtaining,from a remote targeted feature flag configuration server 1203 of thevideo content network 101, feature flag overrides 1223 associated withthe client. A further step includes sending, from the video contentnetwork client 1201, to a remote back-end server 1207 of the videocontent network; the feature flag overrides. For example, Client X 1201passes the feature flag values into back end server A 1207 as queryparams, HTTP headers, via an HTTP post, or the like.

As seen at 1233, 1235, a further step includes, at the video contentnetwork client, obtaining, from the remote back-end server, data to berendered in accordance with an updated feature flag profile includingboth default feature flag values and feature flag values overridden inaccordance with the feature flag overrides. An even further stepincludes rendering the data on the video content network client.

In a non-limiting example, there is no communication or connectivitybetween the back-end server and the config-flag server. The configserver could be, for example, in a protected network where the backendserver could be more open. The backend server could have multipleinstances running around the country, while the config-flag server couldbe centralized. Other embodiments could be architected differently.

In one or more embodiments, the client does not obtain the full list offeature flags back from the back-end service. Rather, the back-endservice executes business logic with the full list of default featureflags modified in accordance with the feature flag overrides. Forexample, refer to FIG. 12. View 1291 shows a simplified default userinterface to be displayed on a client. Fast forward 1295 and reverse1297 are indicative of a variety of features that can be provided.Suppose it is desired to roll out a new a new RECORD CDVR (cloud DVR)button 1299. View 1293 shows a user interface rendered in accordancewith a feature flag that enables the new button. The back-end serverexecutes its code and when it reaches the code segment about whether toinclude the CDVR button, based on the overridden feature flag, itreturns the button 1299 to the client.

It will thus be appreciated that in one or more embodiments,communication 1235 is not a list of flags per se but rather a resultgenerated by the back-end based on the flags. For example, in the caseof the button 1299, what is returned could include a JSON structure orHTML code that instantiates the button on the user's screen. Furtherexamples include new user interface features, new search algorithms thatit is desired to gradually roll out, and the like. In the latterexample, there is, for example, a default search algorithm but a flag isset to use a new search algorithm for some group of customers. The newsearch algorithm is executed on the server 1207 which returns the searchresults at 1235. The overridden flags change what is displayed on theclient from the default such as a new button or different search result.

In one or more embodiments, the remote back-end server retrieves thedefault feature flag values from a feature flag database 1211, as seenat 1227, 1229; generates the updated feature flag profile based on theretrieved default feature flag values and the feature flag overrides, asseen at 1231; and uses business logic to generate the data in accordancewith the updated feature flag profile, as seen at 1233.

In one or more embodiments, the feature flag database 1211 includes aplurality of profiles for a plurality of versions of a plurality ofclients including the video content network client.

The data returned at 1235 can include, for example, data specifying auser interface for the client; or search results setting forth resultsof a search conducted by the back-end server using a non-default searchroutine specified by the feature flag overrides. Indeed, the featureflag overrides and returned data can relate to many different aspects,such as program guide(s) and/or on demand menu(s), bug fixes; searchfeatures; cloud DVR functionality; content recommendations; updates toexisting features (a new search algorithm is a non-limiting example);advertisements; and the like).

In some instances, the video content network client sends a request1202, 1221 to the remote targeted feature flag configuration server uponinitialization to obtain the feature flag overrides. As noted, periodicrequests can be used in some instances. In one or more embodiments, therequest includes account information for an account holder associatedwith the client, and a device identifier for the client. The request canbe implemented, for example, via an application program interface (API)call (RESTFUL is a non-limiting example of an API call).

In some instances, the default feature flag value(s) is/are OFF and thefeature flag overrides turn corresponding features ON. The converse canalso be true, or some features can be default ON and some featuresdefault OFF. Refer to the above discussion of disabling of features fromthe client.

In some embodiments, the remote targeted feature flag configurationserver uses logic to determine the feature flag overrides associatedwith the client based on the account information and the deviceidentifier (for example, finding the client in a target group).

One or more embodiments further include repeating the steps of obtainingthe feature flag overrides, sending the feature flag overrides,obtaining the data to be rendered, and rendering the data on the clientfor a plurality of additional clients to implement a gradual featurerollout. As discussed elsewhere herein, examples of types of rolloutsinclude whitelisting; canary; A/B experimentation; employees first;subset of customers; all customers; employing a new search feature ononly on a subset of clients and on only on a subset of accounts within agiven client type; by individual account(s); for an engineer/developmentlab; and the like.

FIG. 13A shows a flow chart of exemplary logic that can be implementedon server 1203. The logic begins at 1301. At 1303, determine whether theuser is in a group that is to have custom feature flags. If YES, proceedto 1305 and set the flag override(s) for that user. The processcontinues at 1307, awaiting the next client communication. Id the useris not in a group to have custom flags (NO branch of decision block1303), proceed t0 1307 without any flag override(s). FIG. 13B shows anon-limiting example of how a group can be populated. The logic beginsat 1311. At 1313, set the initial percentage equal to zero. At 1315,increment the percentage by the desired amount (say, roll out to thefirst 5%). Adjust group membership by assigning 5% of viewers to agradual rollout group. As seen at decision block 1307, continue untilthe desired percentage of users are in the group; add another 5% if themaximum desired percentage has not been reached. This loop of checkingand incrementing is repeated, for example, on a time-delayed basis, suchthat 5% of users have the feature the first week, 10% the second week,and so on. Other percentages and time intervals can be sued in otherembodiments.

Many different features can be provided, such as thick server/thinclient with all business logic in the back end and the front end onlyfunctioning to view information, with the thick service implementing thenew features. As noted, the client can be located in a premises of thecustomer of the MSO, or elsewhere.

In another aspect, a video content network client 1201 includes a memory730; and at least one processor 720, coupled to the memory, andoperative to: obtain, from a remote targeted feature flag configurationserver of the video content network, feature flag overrides associatedwith the client; send, from the video content network client, to aremote back-end server of the video content network; the feature flagoverrides; obtain, from the remote back-end server, data to be renderedin accordance with an updated feature flag profile including bothdefault feature flag values and feature flag values overridden inaccordance with the feature flag overrides; and render the data on thevideo content network client, as discussed with regard to the abovemethod.

In still another aspect, a video content network system is connected toat least one client. The client(s) can be workpiece(s) separate from thesystem (in other embodiments the client(s) can be part of the system).The system includes a remote targeted feature flag configuration server1203 that provides, to the client 1201, feature flag overridesassociated with the client, as seen at 1223. Also included is a remoteback-end server 1207 that obtains, from the client, the feature flagoverrides, as seen at 1225, and provides, to the client, data 1235 to berendered in accordance with an updated feature flag profile includingboth default feature flag values and feature flag values overridden inaccordance with the feature flag overrides.

One or more embodiments also include a feature flag database 1211associated with the remote back-end server. The remote back-end server:retrieves the default feature flag values from the feature flagdatabase, as 1t 1227, 1229; generates the updated feature flag profilebased on the retrieved default feature flag values and the feature flagoverrides, as at 1231; and uses business logic to generate the data inaccordance with the updated feature flag profile, as at 1233.

Feature flag database 1211 includes, for example, a plurality ofprofiles for a plurality of versions of a plurality of clients includingthe at least one client.

The data sent at 1235 can include, for example, data specifying a userinterface for the client; and/or search results setting forth results ofa search conducted by the back-end server using a non-default searchroutine specified by the feature flag overrides.

In one or more embodiments, the remote targeted feature flagconfiguration server 1203 obtains a request from the at least one clientupon initialization (i.e., of the client) to cause the remote targetedfeature flag configuration server to provide the feature flag overrides.The request includes, for example, account information for an accountholder associated with the client, and a device identifier for theclient. The request is implemented, for example, via an applicationprogram interface (API) call.

In some cases, the remote targeted feature flag configuration server1203 uses logic to determine the feature flag overrides associated withthe client based on the account information and the device identifier.See, e.g., FIGS. 13A and 13B and accompanying text.

The default feature flag values can, for example, be OFF and the featureflag overrides can, for example, turn corresponding features ON.

The video content network system can be connected to a plurality ofclients including the at least one client; the remote targeted featureflag configuration server can provides the feature flag overrides toadditional ones of the plurality of clients; and the remote back-endserver can obtain, from the additional ones of the plurality of clients,the feature flag overrides, and can provide, to the additional ones ofthe plurality of clients, the data to be rendered in accordance with theupdated feature flag profile including both default feature flag valuesand feature flag values overridden in accordance with the feature flagoverrides, so as to allow for a gradual rollout or the like.

In a further aspect, an exemplary method includes the functionality justdescribed with respect to the video content network system; i.e.,providing, from a remote targeted feature flag configuration server 1203of a video content network system, to a client 1201, feature flagoverrides associated with said client; obtaining, at a remote back-endserver 1207, from said client, said feature flag overrides; andproviding, from said remote back-end server, to said client, data to berendered in accordance with an updated feature flag profile comprisingboth default feature flag values and feature flag values overridden inaccordance with said feature flag overrides (optionally including any ofthe additional functionality discussed above).

The functionality at the client can be implemented, for example, byrendering code in a browser and/or via an “app” executing on the client.The browser executable code and/or the “app” can be provided, forexample, from an MSO.

It should also be noted that, in general, methods can include stepsperformed by the remote targeted feature flag configuration server 1203,the client 1201, the remote back-end server 1207, or any combination oftwo or more thereof.

System and Article of Manufacture Details

The invention can employ hardware aspects or a combination of hardwareand software aspects. Software includes but is not limited to firmware,resident software, microcode, etc. One or more embodiments of theinvention or elements thereof can be implemented in the form of anarticle of manufacture including a machine readable medium that containsone or more programs which when executed implement such step(s); that isto say, a computer program product including a tangible computerreadable recordable storage medium (or multiple such media) withcomputer usable program code configured to implement the method stepsindicated, when run on one or more processors. Furthermore, one or moreembodiments of the invention or elements thereof can be implemented inthe form of an apparatus including a memory and at least one processorthat is coupled to the memory and operative to perform, or facilitateperformance of, exemplary method steps.

Yet further, in another aspect, one or more embodiments of the inventionor elements thereof can be implemented in the form of means for carryingout one or more of the method steps described herein; the means caninclude (i) specialized hardware module(s), (ii) software module(s)executing on one or more general purpose or specialized hardwareprocessors, or (iii) a combination of (i) and (ii); any of (i)-(iii)implement the specific techniques set forth herein, and the softwaremodules are stored in a tangible computer-readable recordable storagemedium (or multiple such media). The means do not include transmissionmedia per se or disembodied signals per se. Appropriate interconnectionsvia bus, network, and the like can also be included.

FIG. 7 is a block diagram of a system 700 that can implement at leastsome aspects of the invention, and is representative, for example, ofone or more of the servers shown in the figures. As shown in FIG. 7,memory 730 configures the processor 720 to implement one or moremethods, steps, and functions (collectively, shown as process 780 inFIG. 7). The memory 730 could be distributed or local and the processor720 could be distributed or singular. Different steps could be carriedout by different processors.

The memory 730 could be implemented as an electrical, magnetic oroptical memory, or any combination of these or other types of storagedevices. It should be noted that if distributed processors are employed,each distributed processor that makes up processor 720 generallycontains its own addressable memory space. It should also be noted thatsome or all of computer system 700 can be incorporated into anapplication-specific or general-use integrated circuit. For example, oneor more method steps could be implemented in hardware in an ASIC or viaa field-programmable gate array (FPGA) rather than using firmware.Display 740 is representative of a variety of possible input/outputdevices (e.g., keyboards, mice, and the like). Every processor may nothave a display, keyboard, mouse or the like associated with it.

As is known in the art, part or all of one or more aspects of themethods and apparatus discussed herein may be distributed as an articleof manufacture that itself includes a tangible computer readablerecordable storage medium having computer readable code means embodiedthereon. The computer readable program code means is operable, inconjunction with a computer system (including, for example, system 700or the like), to carry out all or some of the steps to perform themethods or create the apparatuses discussed herein. A computer readablemedium may, in general, be a recordable medium (e.g., floppy disks, harddrives, compact disks, EEPROMs, or memory cards) or may be atransmission medium (e.g., a network including fiber-optics, theworld-wide web, cables, or a wireless channel using time-divisionmultiple access, code-division multiple access, or other radio-frequencychannel). Any medium known or developed that can store informationsuitable for use with a computer system may be used. Thecomputer-readable code means is any mechanism for allowing a computer toread instructions and data, such as magnetic variations on a magneticmedia or height variations on the surface of a compact disk. The mediumcan be distributed on multiple physical devices (or over multiplenetworks). As used herein, a tangible computer-readable recordablestorage medium is defined to encompass a recordable medium, examples ofwhich are set forth above, but is defined not to encompass atransmission medium or disembodied signal.

The computer systems and servers and other pertinent elements describedherein each typically contain a memory that will configure associatedprocessors to implement the methods, steps, and functions disclosedherein. The memories could be distributed or local and the processorscould be distributed or singular. The memories could be implemented asan electrical, magnetic or optical memory, or any combination of theseor other types of storage devices. Moreover, the term “memory” should beconstrued broadly enough to encompass any information able to be readfrom or written to an address in the addressable space accessed by anassociated processor. With this definition, information on a network isstill within a memory because the associated processor can retrieve theinformation from the network.

Accordingly, it will be appreciated that one or more embodiments of thepresent invention can include a computer program product comprisingcomputer program code means adapted to perform one or all of the stepsof any methods or claims set forth herein when such program is run, forexample, on a virtualized or non-virtualized hardware serverimplementing one or more of the servers shown in the figures (servers1203 and 1207 are non-limiting examples) or on a client such as client1201, and that such program may be embodied on a tangible computerreadable recordable storage medium. As used herein, including theclaims, unless it is unambiguously apparent from the context that onlyserver software is being referred to, a “server” includes a physicaldata processing system (for example, system 700 as shown in FIG. 7)running one or more server programs. It will be understood that such aphysical server may or may not include a display, keyboard, or otherinput/output components. Furthermore, as used herein, including theclaims, a “router” includes a networking device with both software andhardware tailored to the tasks of routing and forwarding information.

Furthermore, it should be noted that any of the methods described hereincan include an additional step of providing a system comprising distinctsoftware modules embodied on one or more tangible computer readablestorage media. All the modules (or any subset thereof) can be on thesame medium, or each can be on a different medium, for example. Themodules can include any or all of the components shown in the figures(e.g. modules/sub-modules to implement the elements in FIGS. 10 and 11.The method steps can then be carried out using the distinct softwaremodules of the system, as described above, executing on one or morehardware processors (e.g., a hardware processor or server located in thepremises, head end, regional data center 1048, national data center1098, in the cloud, or on a remote/roaming client). Further, a computerprogram product can include a tangible computer-readable recordablestorage medium with code adapted to be executed to carry out one or moremethod steps described herein, including the provision of the systemwith the distinct software modules.

Accordingly, it will be appreciated that one or more embodiments of theinvention can include a computer program including computer program codemeans adapted to perform one or all of the steps of any methods orclaims set forth herein when such program is implemented on a processor,and that such program may be embodied on a tangible computer readablerecordable storage medium. Further, one or more embodiments of thepresent invention can include a processor including code adapted tocause the processor to carry out one or more steps of methods or claimsset forth herein, together with one or more apparatus elements orfeatures as depicted and described herein.

Although illustrative embodiments of the present invention have beendescribed herein with reference to the accompanying drawings, it is tobe understood that the invention is not limited to those preciseembodiments, and that various other changes and modifications may bemade by one skilled in the art without departing from the scope orspirit of the invention.

1. A method comprising: at a video content network client for renderinginformation from a remote back-end server, obtaining, from a remotetargeted feature flag configuration server of said video contentnetwork, feature flag overrides associated with said client; sending,from said video content network client for rendering said informationfrom said remote back-end server, said feature flag overrides to theremote back-end server of said video content network; at said videocontent network client for rendering said information from said remoteback-end server, obtaining, from said remote back-end server, data to berendered in accordance with an updated feature flag profile comprisingboth default feature flag values and feature flag values overridden inaccordance with said feature flag overrides; and rendering said data onsaid video content network client.
 2. The method of claim 1, furthercomprising said remote back-end server: retrieving said default featureflag values from a feature flag database; generating said updatedfeature flag profile based on said retrieved default feature flag valuesand said feature flag overrides; and using business logic to generatesaid data in accordance with said updated feature flag profile.
 3. Themethod of claim 2, wherein said feature flag database includes aplurality of profiles for a plurality of versions of a plurality ofclients including said video content network client.
 4. The method ofclaim 3, wherein said data comprises data specifying a user interfacefor said client.
 5. The method of claim 3, wherein said data comprisessearch results setting forth results of a search conducted by saidback-end server using a non-default search routine specified by saidfeature flag overrides.
 6. The method of claim 1, wherein said videocontent network client sends a request to said remote targeted featureflag configuration server upon initialization to obtain said featureflag overrides.
 7. The method of claim 6, wherein said request includesaccount information for an account holder associated with said client,and a device identifier for said client.
 8. The method of claim 7,wherein said request is implemented via an application program interface(API) call.
 9. The method of claim 8, further comprising said remotetargeted feature flag configuration server using logic to determine saidfeature flag overrides associated with said client based on said accountinformation and said device identifier.
 10. The method of claim 1,wherein said default feature flag values comprise OFF and said featureflag overrides turn corresponding features ON.
 11. The method of claim1, wherein said default feature flag values comprise ON and said featureflag overrides turn corresponding features OFF.
 12. The method of claim1, further comprising repeating said steps of obtaining said featureflag overrides, sending said feature flag overrides, obtaining said datato be rendered, and rendering said data for a plurality of additionalclients to implement a gradual feature rollout.
 13. A video contentnetwork client comprising: a memory; and at least one processor, coupledto said memory, and operative to: obtain, from a remote targeted featureflag configuration server of said video content network, feature flagoverrides associated with said client; send, from said video contentnetwork client, to a remote back-end server of said video contentnetwork; said feature flag overrides; obtain, from said remote back-endserver, data to be rendered in accordance with an updated feature flagprofile comprising both default feature flag values and feature flagvalues overridden in accordance with said feature flag overrides; andrender said data on said video content network client.
 14. A videocontent network system connected to at least one client, said systemcomprising: a remote targeted feature flag configuration server thatprovides, to the client, feature flag overrides associated with saidclient; and a remote back-end server that obtains, from said client,said feature flag overrides, and provides, to the client, data to berendered in accordance with an updated feature flag profile comprisingboth default feature flag values and feature flag values overridden inaccordance with said feature flag overrides, wherein the client isconfigured to render said data from said remote back-end server.
 15. Thevideo content network system of claim 14, further comprising a featureflag database associated with said remote back-end server, wherein saidremote back-end server: retrieves said default feature flag values fromsaid feature flag database; generates said updated feature flag profilebased on said retrieved default feature flag values and said featureflag overrides; and uses business logic to generate said data inaccordance with said updated feature flag profile.
 16. The video contentnetwork system of claim 15, wherein said feature flag database includesa plurality of profiles for a plurality of versions of a plurality ofclients including the at least one client.
 17. The video content networksystem of claim 16, wherein said data comprises data specifying a userinterface for said client.
 18. The video content network system of claim16, wherein said data comprises search results setting forth results ofa search conducted by said back-end server using a non-default searchroutine specified by said feature flag overrides.
 19. The video contentnetwork system of claim 14, wherein said remote targeted feature flagconfiguration server obtains a request from the at least one client uponinitialization to cause said remote targeted feature flag configurationserver to provide said feature flag overrides.
 20. The video contentnetwork system of claim 19, wherein said request includes accountinformation for an account holder associated with the client, and adevice identifier for the client.
 21. The video content network systemof claim 20, wherein said request is implemented via an applicationprogram interface (API) call.
 22. The video content network system ofclaim 21, wherein said remote targeted feature flag configuration serveruses logic to determine said feature flag overrides associated with theclient based on said account information and said device identifier. 23.The video content network system of claim 14, wherein said defaultfeature flag values comprise OFF and said feature flag overrides turncorresponding features ON.
 24. The video content network system of claim14, wherein said default feature flag values comprise ON and saidfeature flag overrides turn corresponding features OFF.
 25. The videocontent network system of claim 14, wherein: said system is connected toa plurality of clients including the at least one client; said remotetargeted feature flag configuration server provides said feature flagoverrides to additional ones of said plurality of clients; and saidremote back-end server obtains, from said additional ones of saidplurality of clients, said feature flag overrides, and provides, to saidadditional ones of said plurality of clients, said data to be renderedin accordance with said updated feature flag profile comprising bothdefault feature flag values and feature flag values overridden inaccordance with said feature flag overrides.
 26. A method comprising:providing, from a remote targeted feature flag configuration server of avideo content network system, to a client configured to renderinformation from a remote back-end server, feature flag overridesassociated with said client; obtaining, at said remote back-end server,from said client, said feature flag overrides; and providing, from saidremote back-end server, to said client, data to be rendered inaccordance with an updated feature flag profile comprising both defaultfeature flag values and feature flag values overridden in accordancewith said feature flag overrides.